home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group92c.txt
/
000036_icon-group-sender _Sun Oct 4 20:38:26 1992.msg
< prev
next >
Wrap
Internet Message Format
|
1993-01-04
|
1KB
Received: by cheltenham.cs.arizona.edu; Sun, 25 Oct 1992 18:23:54 MST
Date: 4 Oct 92 20:38:26 GMT
From: agate!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!uchinews!quads!goer@ucbvax.Berkeley.EDU (Richard L. Goerwitz)
Organization: University of Chicago Computing Organizations
Subject: Re: storing objects
Message-Id: <1992Oct4.203826.22606@midway.uchicago.edu>
References: <9210040357.AA05603@gremlin>
Sender: icon-group-request@cs.arizona.edu
To: icon-group@cs.arizona.edu
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
wgg@CS.UCSD.EDU (William Griswold) writes:
>
>Well, you might be able to exploit the properties of your specific tables.
>For example, if your keys and elements are all ``printable'', then...
What they are are LR(1)-generated action and goto tables. If I don't opti-
mize (or do so at run-time), then I can do what you suggest. The trouble
is that one of the big optimizations that takes some time to sort out is
based on the property that rows in the action table are often the same, so
that one can store pointers to one single structure, instead of repeating
identical rows.
--
-Richard L. Goerwitz goer%midway@uchicago.bitnet
goer@midway.uchicago.edu rutgers!oddjob!ellis!goer